MaxInUse[n]
Integer
Not specified
Purpose
The MaxInUse[n] parameter specifies the maximum number of connections that can be opened for the corresponding value of the TcpPort[n] parameter only when the value of the ApplicationType parameter is set to RestServices, WebEnabledForms, WebServices, or HtmlDocuments.
The MaxInUse parameter with no specified suffix is the limit for a ConnectionGroup associated with an entry with the TcpConnection parameter; it is not a global limit.
The MaxInUse[n] parameter defines the limit of outstanding requests for a single connection group; that is, the sum of queued and active requests. The total number of outstanding requests for a web application is the sum of the MaxInUse[n] suffix values for all of the connection groups specified for that application.
This parameter is the only jadehttp.dll configuration setting that affects the dynamic worker pool scaling. If this value is too small, it will prevent the spawning of new REST service applications. The value must be large enough to allow enough connections between IIS and Jade so the queue depth remains greater than the
In general, most REST server usage patterns would be well‑served by a MaxInUse parameter value that is 10 times larger than the queue depth limit, with a value not less than 50.
The MaxInUse parameter is the only configuration setting the affects how often the system will respond with a “Server Unavailable” 503 response. In a direct HTTP configuration, all requests are queued. This parameter controls how many connections (sockets) to keep open when they are not in use. Given the speed at which sockets can be created, this value has no real effect on system performance, and it is entirely reasonable to set it its minimum value of 1.
For more details, see "
Note
The value of the MaxInUse parameter is forced to be equal to or greater than the value of the MinInUse parameter.
